fix: use consistent cert common name - #166
Merged
Merged
Conversation
Use the hex-encoded asset name as the TLS cert common name both when generating the cert and when populating the CRL Signed-off-by: Aurora Gaffney <aurora@blinklabs.io>
agaffney
force-pushed
the
fix/client-serial
branch
from
October 12, 2025 13:14
96597a1 to
ccfaf73
Compare
wolf31o2
approved these changes
Oct 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use the hex-encoded asset name as the TLS cert common name both when generating the cert and when populating the CRL